Voyager allows the user to define multiple Fastlink buttons. These are simply defined by filling in the button Label on the left, and the URL that is associated with it on the right.

Voyager's Fastlinks can be shown or hidden by toggling Show Fastlinks? in the Settings menu.

Here you can configure the Proxy Server Voyager is to use. A Proxy Server can speed up the browing of commonly-accessed pages, since it keeps the page locally on it. When a request for the page - say, www.yahoo.com - arrives, the proxy server simply sends what it has stored to the browser if the original site has not changed.

• HTTP is the proxy Host and Port number which Voyager is to connect to for all WWW retrieval. It is not neccessary to use a Proxy Server for HTTP, but recommended.

• FTP is the proxy that Voyager is to connect to for all FTP data transfers. This is often the same as the WWW proxy server.

• Gopher and WAIS are generally used a lot less than HTTP and FTP. Gopher is an alternative file download method.

• No Proxy for hosts and WAIS sometimes a server may not require you to use a proxy for certain reasons. This option allows to enter the host/s where proxies will not be used.

  Useful if you have a web server locally, or at your ISP and don't want it too be fetched by the proxy (would only mean more overhead in that case, and no benefit).

  Enter as: host1.domain,host2.domain,host3.domain (The formula is host:port).

• Maximum number of connections allows you to set the number of connections Voyager will open to download files. This doesn't always speed up web browsing, however, and can even cause buffer overflows within your TCP/IP stack.

  The LED's on the Voyager main interface should the number of connections open.

• Directory allows you define your cache directory. This is where cached files are stored.

  You could choose ram:, but your cache would be lost everytime you reboot. We suggest you put the cache on a partition which is quite small, in case the computer crashes whilst you are writing to the cache.

• Maximum Size defines the largest size (in kilobytes) that Voyager's disk cache may grow to. Once it gets to this size, older documents are removed from the cache to make way for newer ones.

• Empty cache now allows you to delete the current on-disk cache.

• Verify configures Voyager's cache verification. Voyager can check when you access a document that resides in its cache to see if it has been updated since your last access to it. If it has not been changed, it displayed the cached version. You can tell Voyager to verify the documents Once per session, Upon every access to the page, or Never (always use the cache).

• Maximum Size defines the largest size (in kilobytes) that Voyager's memory cache may grow to. Once it gets to this size, older documents are removed from the cache to make way for newer ones.

• Empty cache now allows you to delete the current on-disk cache.

• Cache Images? cache images within memory. If you have an AGA or ECS based Amiga, only cache images if you have a lot of spare memory! We recommend at least 10MB of spare memory, perhaps more.

• Ask before sending a mailto: form?  - when you create a email within Voyager (via mailto:) this option, if checked, will confirm that you really want to send the mail before it is despatched.

• Warn before posting unsecure form data?  - this option will ask you to confirm that you want to send form data via a unsecure, non-https server.

• Don't send Referer: HTTP header  - "Referer" is a header sent in HTTP requests which will show the URL from which link was estabilished.

  Example:

  www.porn.com has a "A HREF" to www.nice.site.org. If the user clicks on the www.nice.site.org link on www.porn.com, the Referer: header in the HTTP request sends this to www.nice.site.org with "www.porn.com" in it. Tthis can be used for tracking people and is widely used by banner systems.

• Don't send email address as FTP anon password  - if you connect to an FTP server they often take your email address for anonymous ftp login, which means that they have your email address on their records.

• Cookie handling - Temporary  - you can reject, ask (VNG will ask you if you want to accept a cookie) or accept any server asking for cookie information.

• Cookie handling - Persistant  - you can reject, ask (VNG will ask you if you want to accept a cookie) or accept any server asking for cookie information.

SSL not only encrypts transfer of an online transaction but also "certifies" that the server is the one which it pretends to be. Thus, every SSL server has a "certificate", which is (cryptographically) signed by a "Certification Authority". Browsers now ship with a set of Certificates representing "Certification Authority".

Therefore, if Voyager hits a site which presents a certificate, it can look up which "Certification Authority" has signed the cert, then looks into it's database of known CAs and can compare.

You can edit CERTS to add extra certificates of new CAs, or even accept a site which presents a certificate which isn't signed by a CA, or by an unknwon CA (it will ask).

Voyager currently supports mailto: links to send email to people on the net, and can access an NNTP news server to allow you to browse Usenet newsgroups. Here is where you can configure your identity to show the rest of the world.

• Your email address is required so that people can write back to you. Make sure this is correct!

• Your Real Name is optional, but most people on the net prefer to know who they are conversing with.

• Organization is an optional field for anyone using Voyager within a business to fill in their company name for email/news.

• SMTP (mail) server and NNTP (news) are the servers which Voyager needs to talk to in order to send the mail or news that you have composed to the correct recipient. If you have any problems with these, your ISP should be able to help you.

• Mail/News:  - when you come across a "mailto:" form, you can write an email to the recipient. You can do this internally (select "internal"), using Microdot-II or externally (choose "external").

• Telnet app defines an application to be launched when you click on a telnet: link within Voyager. %h sends the hostname in the link to the telnet application, and %p the port (if any). At Vaporware, of course, we recommend that you use AmTelnet %h %p.